sql: render "record" composite columns with the JSON tree viewer [UX-1330]#2533
Merged
Conversation
Contributor
✅ Clean — no registry drift, off-token colours, or ad-hoc classesApp:
Generated by lookout audit-changes. |
malinskibeniamin
approved these changes
Jun 25, 2026
…1330] The backend now labels composite (struct) columns "record"/"record[]" instead of "json"/"json[]". Map those type strings to the json display kind so composite cells keep the nested JSON tree viewer and the catalog tree/cell popover show the "record" label.
The backend now appends an actionable hint after a blank line. Split it off the error message and render it in the existing styled hint slot below the alert, instead of inline in the message body.
Show the hint in an info Alert with a lightbulb icon and a "Hint" title instead of loose muted text, so it reads clearly as guidance rather than part of the error.
…data only [UX-1330]
c-julin
force-pushed
the
ux-1330-sql-record-type-label
branch
from
a6ae872 to
0233d02
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
The SQL backend is changing the column type label for composite (struct) columns from
json/json[]torecord/record[]. This updates the frontend renderer to recognize the new labels.columnKindForPgTypenow mapsrecord/record[]to the existingjsondisplay kind, so composite cells keep the nested JSON tree viewer and the catalog tree / cell popover surface the accuraterecordlabel instead ofjson.Why
Labeling these columns
jsonled Postgres users to try JSON arrow operators (->,->>), which the engine rejects — composite columns are accessed with(col).field. Therecordlabel stops implying unsupported JSON semantics. Cell values are still rendered as JSON for readability; only the type label changes.Paired change
Backend counterpart (must land together): redpanda-data/console-enterprise#803
Tests
vitest runonsql-types.test.ts+catalog-tree.test.tsx— 33 passed.UX-1330